projects / xen.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 37e7876) | patch
[IA64] work around ENOSYS vs EINVAL in ioremap
authorawilliam@xenbuild.aw <awilliam@xenbuild.aw>
Tue, 23 May 2006 23:05:27 +0000 (17:05 -0600)
committerawilliam@xenbuild.aw <awilliam@xenbuild.aw>
Tue, 23 May 2006 23:05:27 +0000 (17:05 -0600)
commitbc77a64b00d1b014c495ba2465a15554f1189170
tree0fb9d1328025c49a530cb68473e8626e82ec08b0tree | snapshot
parent37e787619ef10cdaaad91e0f886e87a8da31449ecommit | diff
[IA64] work around ENOSYS vs EINVAL in ioremap

We should not panic the domain for an EINVAL return from the ioremap
hyerpcall.  This was only meant for ENOSYS.  Long term this is probably
not the best place for this kind of sanity checking.

Signed-off-by: Alex Williamson <alex.williamson@hp.com>
linux-2.6-xen-sparse/include/asm-ia64/hypercall.h diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.